Here's what I've determined...

In my testing, the last commit that didn't experience the status bar display bug was "d137585" The issue appears to begin with "1b6a029"

The last commit to retain the game's original aspect ratio was "4f97927" The stretched widescreen look begins with "c708329" Based on a casual glance at the details of the latter commit, I think the stretched image is not intended.

I don't currently have a Atlassian/Bitbucket account to report these issues, so if anyone from RetroPie does have an account already and feels like reporting these two issues, it would be much appreciated. It looks like the active Repo on Bitbucket doesn't currently accept reporting of Issues, so I don't know if it is possible to let the Devs know about these issues.

As far as the need for triplicate (identical) files for each of: audiohed, auidiot, vgadict, vgagraph, and vgahead - one for each episode of the "Spear of Destiny" expansion pack... I don't know what to say. Those were not necessary when I first installed Wolf4SDL, way back in 2021. For that matter, ECWolf (a fork of Wolf4SDL, if I'm not mistaken) only requires one of each, as far as I can tell, from my testing of it on Windows. Not sure if the Wolf4SDL Devs really intended this, but it seems like an odd choice if they did.

@joprace said in How do i access this:

Why cant i access retropie setup?

Please tell us more about your system as outlined in https://retropie.org.uk/forum/topic/3/read-this-first

Cannot use the Bluetooth and RetroPie-setup menu in Armbian, any input and it crashes while trying to navigate. If you preset Bluetooth connections within the OS, it runs all games and controls really well.

PSX, all runs well
N64, mid range games run well.
Dreamcast, lower end games run well.

Sadly not perfect yet due to Bluetooth imperfections in the menu and need N64 resolution manual preset when swapping to different quality monitor... Just that :(

#________________________________________#

Managed to install RetroPie successfully on Dietpi OS.
Still working out:

[solved] why the N64 hotkey doesn't work, can't exit
... Disabled '0' mupen64plus hotkey in ~/all/autoconf.ini
... Added J0B12/B11 at emulation Stop in ~/N64/autoconf.ini [solved] why PSX doesn't launch, black screen
... Replaced all my BIOS files [solved]why NES doesn't run, returns to ES
... Used corrupted roms without headers [solved] why Dreamcast won't show in ES
... Had .7z files in the rom folder. Unzipped the files

@mitu Completely agree. As usual, I mess with stuff too much sometimes. It is hooked up as you have said, the primary display is hooked up to the HDMI directly beside the USB-C power port.

@retropieuser555 @windg thanks for all the responds i solved the problem

@ganatbasa please add some more info about your system as detailed in https://retropie.org.uk/forum/topic/3/read-this-first

It sounds like you may have acquired a system pre-configured and "ready-to-go." Note that, because it is not practical to troubleshoot a system that neither you nor we have any idea how is configured, third-party builds are officially not supported in any capacity. If that is indeed the case, you'll need to start over with the default, official image from https://retropie.org.uk/download. Start here: https://retropie.org.uk/docs/First-Installation/

(Unofficially, it sounds like your aspect_ratio_index may be misconfigured in /opt/retropie/configs/all/retroarch.cfg or possible elsewhere.)

https://retropie.org.uk/docs/Shaders-and-Smoothing/

Looks like the files (.deb packages) downloaded by apt are corrupted. Try removing them with apt clean or directly removing the .deb files from /var/cache/apt/archives - then installing again the desktop.

I tried the development version of 2.6.0 (=before it was released) on a RPi4 and 11th hour and Chewy: Esc from F5 worked well. Glad to know ScummVM devs are now satisfied with the quality and tagged 2.6.0 as release. :)

@dankcushions got the both to work used different files and now work cheers

@Hyruleslink
Do you know what version of RetroArch you are running? Its usually in the bottom left somewhere when you are in the UI (Hotkey + X usually)

It might help to paste your retroarch.cfg file on pastebin or similar in case there is something obvious.

@ciel Please provide details from your set-up and a log of the errors you are getting (See RetroPie-Setup/logs). Please put the logfile on a pastebin site rather than directly in the forum.

https://retropie.org.uk/forum/topic/3/read-this-first

@chaoseffect said in lr-flycast new GitHub repository source for setup script?:

I have ports 1 and 2 set to "keyboard" in the RetroArch menu, and I think that's it for keyboard settings. The keyboard works fine for me for player 1, and I was just curious if this update would bring a core option for keyboard indices so that a separate keyboard could be used for player 2.

I think that's the RetroPad -> Emulator core part settings, i.e. the core expects a Keyboard type input from Port 1 (2), the Device -> RetroPad mapping is done by RetroArch.
Usually 1 keyboard can be used for 2 players (as explained here), but I'm not sure 2 keyboards can be used independently (via dev index, how gamepads are handled). This depends on the input driver used, I know some of them don't support it (like Windows winraw). RetroPie should use the udev driver, so it might be supported, but I don't have 2 keyboards right now to test.

@mitu Thanks!!! I will try this :P

I'm not familiar with Pegasus, but I don't think that it's limited to 'command line' , it should work in the desktop env. It may need a configuration file to start ?

I have found the holy grail in this repo line:
https://github.com/meleu/RetroPie-joystick-selection/blob/master/jsfuncs.sh#L345

Basically in order to change the index, we should just edit /opt/retropie/configs/all/retroarch.cfg at this line:
input_player1_joypad_index = "some_index_number"

or whatever input player you want. NOTE: i didn't tested it yet, but this might work.

@greenhawk84
I remember reading in the github page somewhere there was an update involving the joy2key package and you may need to manually update this package.

EDIT: Found the related thread:
https://retropie.org.uk/forum/topic/31092/controller-no-longer-works-in-retropie-setup-launching-menu-es-themes

How exactly did you check the memory? Fake cards report a bigger size than they actually are. You'll only notice it after you write more than their actual size to them, as the exceeding data will be lost, often without any error messages if the fake card was done well.

If you can boot to RetroPie's command line, you can try to install the tool f3 and test the card with that:

sudo apt install f3 # install the tool cd # change to home directory makedir test # create a test directory f3write test # write 1 GB sized test files until the card is full f3read test # read the files' test patterns rm -r test # remove the test directory

It will test the actual amount of data that can successfully be written to the card and read again.